Install PAM modules and systemd units into /usr
Since Debian trixie all files need to be installed into their canonical
location under /usr.
Origin: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=
1061348
Forwarded: https://github.com/MariaDB/server/pull/4065
Gbp-Pq: Name install-files-into-usr.patch
cmake: add support for reproducible buildS
We should use relative path not absolute path. We can use target without
breaking reproducibility.
This patch can be removed once MariaDB ships with Mroonga v12.00+ that has
https://github.com/mroonga/mroonga/commit/
27caeb9b8ce7fa432b1251eca475b517c6902a6c
Origin: https://github.com/mroonga/mroonga/issues/298#issuecomment-
1030815927
Bug: https://github.com/mroonga/mroonga/issues/298
Forwarded: not-needed
Gbp-Pq: Name mroonga-mrn-lib-dirs-path-reproducible-build.patch
mariadb (1:11.8.6-4) unstable; urgency=medium
* New AppArmor for mariadbd now in 'enforce' mode. See NEWS for details.
* Additional refinement to make the AppArmor and related autopkgtest as
robust as possible:
- Add patch to have mariadb-test-run not write in
/usr/share/mariadb/mariadb-test/ to not violate the AppArmor profile
- Normalize variables 'aria-checkpoint-interval' and 'aria-recover-options'
to documented defaults as they seem to be effect in Ubuntu binaries now,
while Debian binaries seem to default to zero and empty for an unknown
reason.
- Ensure AppArmor diagnostics run even when autopkgtests fail to catch
potential situations where autopkgtests job 'upstream' violated the
AppArmor profile.
- Simplify AppArmor profile, allow 'mariadb' aliases and unify indentation.
- Extend AppArmor profile to cover all easily testable features
(Closes: #
1130272).
[dgit import unpatched mariadb 1:11.8.6-4]